Create Slotting Rule
Creates a Rule in the referenced Warehouse Rule Set. Hard Rules use
require or forbid and omit strength; soft Rules use prefer or
discourage and require a strength. The existing Slotting lifecycle
schedules any required asynchronous recalculation after the save commits.
Authorizations
Generate a JWT access token through a Custom Global Integration and provide it with each request in the Authorization header prefixed with "Bearer" and then a single space.
Path Parameters
The id of the referenced Warehouse.
The id of the owning SlottingRuleSet.
Query Parameters
Specify fields of the SlottingRule object to include in the response.
all, rule_set, name, relation, strength, priority, merchant_ids, merchants, product_profile_ids, product_profiles, product_profile_match_mode, handling_class_ids, handling_classes, location_profile, subject_readable, location_match_readable, has_conflicts, conflict_detail, created_at, updated_at Specify fields of the SlottingRuleSet object referenced by each Rule.
See the selecting fields page for more information.
Specify fields of the SlottingRuleSet object to include in the response.
all, name, description, is_active, rule_count, has_conflicts, conflicting_rule_count, created_at, updated_at Specify fields of the LocationProfile object referenced by each Rule.
See the selecting fields page for more information.
Specify direct display fields of an included LocationProfile object.
name, description, status, member_count, match_readable, created_at, updated_at Specify direct fields of selected Merchant objects to include under included.Merchant. Add merchants to the root fields parameter to return the relationship. type and id are always returned.
Specify direct fields of an included Merchant object.
code, name, status, created_at, updated_at Specify fields of selected ProductProfile objects to include under included.ProductProfile. Add product_profiles to the root fields parameter to return the relationship. type and id are always returned.
Specify fields of an included ProductProfile object.
basic, all, name, code, conditions, conditions_readable, matched_count, classification, created_at, updated_at Specify direct fields of selected HandlingClass objects to include under included.HandlingClass. Add handling_classes to the root fields parameter to return the relationship. type and id are always returned.
Specify direct fields of an included HandlingClass object.
name, code, sort_order, conditions, conditions_readable, matched_count, classification, created_at, updated_at Body
The body of a Slotting Rule create request. The Warehouse and owning Rule Set come from the path. The Location Profile must belong to that Warehouse and have a ready active revision.
User-visible Rule name.
1 - 255"Regulated aerosols require Hazmat storage"
Hard requirement or advisory preference applied by the Rule.
require, forbid, prefer, discourage "require"
Ready Location Profile in the path Warehouse targeted by the Rule.
x >= 126
Required for prefer and discourage. Omit this property for require
and forbid; explicitly sending it for a hard Rule is rejected.
low, normal, high, critical, null null
Merchant IDs selected by the Rule; null or an empty list means every Merchant.
100x >= 1Product Profile IDs selected by the Rule; an empty list leaves this dimension unrestricted.
100x >= 1How the selected Product Profiles are matched. none requires at least one ID.
any, all, none "any"
Handling Class IDs assigned to the Warehouse; an empty list leaves this dimension unrestricted.
100x >= 1Response
The Slotting Rule was created.
A Rule inside one Warehouse Slotting Rule Set. It selects Products and Merchants, applies a hard or advisory relation, and targets the resolved membership of one ready Location Profile. Conflict fields are the latest durable result of asynchronous Slotting conflict detection.
Direct objects included by specifying nested fields. Relationship trees below these editor selections are never expanded. See the selecting fields page.
Additional metadata pertaining to the response.